Archetypes of delay: An analysis of online developer conversations on delayed work items in IBM Jazz

A widely adopted methodology, agile software development provides enhanced flexibility to actively adjust a project scope. In teams, particularly in distributed environment, developers interact, manage requirements knowledge, and coordinate primarily online collaboration tools. Developer conversations become invaluable sources track understand developers’ interactions around implementation of requirements, as well the progress relative scope planned iterations projects. Although extensive research iteration planning exists, there is lack that leverages developer conversation data delays implementing By using large at IBM, this work aims analyze items (WIs) are delayed derive patterns suggest reasons for delay project. We conducted case study IBM Jazz project, used thematic analysis code time-series, cluster identify differentiated evolution discussions WIs were late vs. not identified six main WI delay. Through semantic within particular clusters we able explain each pattern. comparison non-late WIs, find major reason frequent communication associated with poor management WIs. Similarly, tasks more often delegate children accelerate addition processing requests quickly resolve bottlenecks implementation. Our complements existing bringing evidence useful resource can highlight requirement implementation, recommend dynamics relevant such delays.